How Reply works

Introduction

Reviewed · not yet fact-checked

Understand Reply's capabilities, workflows, product specifications, and rules — and build prospecting, outbound, inbox, and AI SDR systems on top of it.

This site explains what Reply can do and exactly how the product behaves. Reply is a sales engagement platform: sequences that combine email, LinkedIn, call, SMS, WhatsApp, task, and Zapier steps; the Reply Data B2B database for finding prospects; a consolidated inbox with AI-assigned reply categories; MailToaster email warm-up; native CRM integrations (Salesforce, HubSpot, Pipedrive, Copper); the Findy Chrome extension; and Jason AI — an AI SDR that builds and runs campaigns. This documentation is written so a person or an AI agent can decide whether Reply fits a task, understand the rules it will follow, and jump straight to implementation.

Status labels. Every page carries a status. Reviewed pages are grounded in Reply's product documentation; pages still labeled Placeholder are structural scaffolding — treat their detailed claims as unverified until the label is removed.

Follow the journey

Go deeper

How this site is organized

SectionQuestion it answers
StartWhat is Reply, and how do the underlying mechanisms work?
CapabilitiesCan Reply do this?
WorkflowsHow does the complete outcome work — and what should I do in my situation?
How toHow do I configure it — and why did it fail?
BehaviorWhat deterministic logic applies?
SpecificationsWhat is this product object?
ReferenceWhat are the exact values?

Reading this site as a machine

curl https://how.reply.io/llms.txt          # curated index
curl https://how.reply.io/index.json        # site map by section
curl https://how.reply.io/start/agent-index.md   # the agent-oriented summary
# append .md to any page URL for its markdown twin

Build with Reply